Activating Localization Debug Mode
(Undefined variable: General.PlatformName) supports the localization of static and dynamic elements, as well as the localization of customized messages and metadata.
Before localizing in a new language, you need to prepare your environment to easily identify the resources to be localized. To do so, open Vault secrets change the value of the following:
From:
| Key Path | Key Name | Key Value |
|---|---|---|
| kv/<environment>/<application>/app-settings | ebs:debugLocalization | 0; |
To:
| Key Path | Key Name | Key Value |
|---|---|---|
| kv/<environment>/<application>/app-settings | ebs:debugLocalization | 1; |
The table below lists the localization keys:
| Key | Description |
|---|---|
| ebs:uiLocalization | Toggles dynamic UI localization (HTML templates, after generate JavaScript). The immediate result visible in the user interface is the dynamic generation of HTML templates in the optimum format for localization. |
| ebs:dataLocalization | Toggles metadata (data) localization and automatically creates database support for each language. |
| ebs:debugLocalization | Toggles the debug mode. |
| ebs:localizationSchedulerTimeSpan | Interval in milliseconds when checking for external resource updates in the database. |
Once the localization debug mode is activated, the following markers are displayed for both the user interface and the metadata localized values:
✅ - To indicate the localized values.
- To indicate that values are localizable, but no localization has been provided.
- To indicate that the fields allow localization of the data inside the field.